home *** CD-ROM | disk | FTP | other *** search
Text File | 1995-07-06 | 16.3 KB | 414 lines | [TEXT/MPS ] |
- {
- File: DigitalSignature.p
-
- Contains: Digital Signature Interfaces.
-
- Version: Technology: AOCE toolbox 1.02
- Package: Universal Interfaces 2.1 in “MPW Latest” on ETO #18
-
- Copyright: © 1984-1995 by Apple Computer, Inc.
- All rights reserved.
-
- Bugs?: If you find a problem with this file, use the Apple Bug Reporter
- stack. Include the file and version information (from above)
- in the problem description and send to:
- Internet: apple.bugs@applelink.apple.com
- AppleLink: APPLE.BUGS
-
- }
-
- {$IFC UNDEFINED UsingIncludes}
- {$SETC UsingIncludes := 0}
- {$ENDC}
-
- {$IFC NOT UsingIncludes}
- UNIT DigitalSignature;
- INTERFACE
- {$ENDC}
-
- {$IFC UNDEFINED __DIGITALSIGNATURE__}
- {$SETC __DIGITALSIGNATURE__ := 1}
-
- {$I+}
- {$SETC DigitalSignatureIncludes := UsingIncludes}
- {$SETC UsingIncludes := 1}
-
-
- {$IFC UNDEFINED __TYPES__}
- {$I Types.p}
- {$ENDC}
- { ConditionalMacros.p }
-
- {$IFC UNDEFINED __MEMORY__}
- {$I Memory.p}
- {$ENDC}
- { MixedMode.p }
-
- {$IFC UNDEFINED __FILES__}
- {$I Files.p}
- {$ENDC}
- { OSUtils.p }
- { Finder.p }
-
- {$PUSH}
- {$ALIGN MAC68K}
- {$LibExport+}
-
- CONST
- kSIGNewContext = 1900;
- kSIGDisposeContext = 1901;
- kSIGSignPrepare = 1902;
- kSIGSign = 1903;
- kSIGVerifyPrepare = 1904;
- kSIGVerify = 1905;
- kSIGDigestPrepare = 1906;
- kSIGDigest = 1907;
- kSIGProcessData = 1908;
- kSIGShowSigner = 1909;
- kSIGGetSignerInfo = 1910;
- kSIGGetCertInfo = 1911;
- kSIGGetCertNameAttributes = 1912;
- kSIGGetCertIssuerNameAttributes = 1913;
- kSIGFileIsSigned = 2500;
- kSIGSignFile = 2501;
- kSIGVerifyFile = 2502;
-
- kSIGCountryCode = 0;
- kSIGOrganization = 1;
- kSIGStreetAddress = 2;
- kSIGState = 3;
- kSIGLocality = 4;
- kSIGCommonName = 5;
- kSIGTitle = 6;
- kSIGOrganizationUnit = 7;
- kSIGPostalCode = 8;
-
-
- TYPE
- SIGNameAttributeType = INTEGER;
-
- {
- Certificate status codes returned in SIGCertInfo or SIGSignerInfo from
- either SIGGetCertInfo or SIGGetSignerInfo respectively. kSIGValid means that
- the certificate is currently valid. kSIGPending means the certificate is
- currently not valid - but will be. kSIGExpired means the certificate has
- expired. A time is always associated with a SIGCertStatus. In each case the
- time has a specific interpretation. When the status is kSIGValid the time is
- when the certificate will expire. When the status is kSIGPending the time is
- when the certificate will become valid. When the status is kSIGExpired the time
- is when the certificate expired. In the SIGCertInfo structure, the startDate
- and endDate fields hold the appropriate date information. In the SIGSignerInfo
- structure, this information is provided in the certSetStatusTime field. In the
- SIGSignerInfo struct, the status time is actually represented by the SIGSignatureStatus
- field which can contain any of the types below. NOTE: The only time you will get
- a kSIGInvalid status is when it pertains to a SIGSignatureStatus field and only when
- you get a signature that was created after the certificates expiration date, something
- we are not allowing on the Mac but that may not be restricted on other platforms. Also,
- it will not be possible to get a kSIGPending value for SIGSignatureStatus on the Mac but
- possibly allowed by other platforms.
- }
- { Values for SIGCertStatus or SIGSignatureStatus }
-
- CONST
- kSIGValid = 0; { possible for either a SIGCertStatus or SIGSignatureStatus }
- kSIGPending = 1; { possible for either a SIGCertStatus or SIGSignatureStatus }
- kSIGExpired = 2; { possible for either a SIGCertStatus or SIGSignatureStatus
- * possible only for a SIGSignatureStatus }
- kSIGInvalid = 3;
-
-
- TYPE
- SIGCertStatus = INTEGER;
-
- SIGSignatureStatus = INTEGER;
-
- { Gestalt selector code - returns toolbox version in low-order word }
-
- CONST
- gestaltDigitalSignatureVersion = 'dsig';
-
- { Number of bytes needed for a digest record when using SIGDigest }
- kSIGDigestSize = 16;
-
-
- TYPE
- SIGDigestData = ARRAY [0..kSIGDigestSize-1] OF Byte;
- SIGDigestDataPtr = ^Byte;
-
- SIGCertInfo = RECORD
- startDate: LONGINT; { cert start validity date }
- endDate: LONGINT; { cert end validity date }
- certStatus: SIGCertStatus; { see comment on SIGCertStatus for definition }
- certAttributeCount: LONGINT; { number of name attributes in this cert }
- issuerAttributeCount: LONGINT; { number of name attributes in this certs issuer }
- serialNumber: Str255; { cert serial number }
- END;
-
- SIGCertInfoPtr = ^SIGCertInfo;
-
- SIGSignerInfo = RECORD
- signingTime: LONGINT; { time of signing }
- certCount: LONGINT; { number of certificates in the cert set }
- certSetStatusTime: LONGINT; { Worst cert status time. See comment on SIGCertStatus for definition }
- signatureStatus: SIGSignatureStatus; { The status of the signature. See comment on SIGCertStatus for definition}
- END;
-
- SIGSignerInfoPtr = ^SIGSignerInfo;
-
- SIGNameAttributesInfo = RECORD
- onNewLevel: BOOLEAN;
- filler1: BOOLEAN;
- attributeType: SIGNameAttributeType;
- attributeScript: ScriptCode;
- attribute: Str255;
- END;
-
- SIGNameAttributesInfoPtr = ^SIGNameAttributesInfo;
-
- SIGContextPtr = Ptr;
-
- SIGSignaturePtr = Ptr;
-
- {
- Certificates are always in order. That is, the signers cert is always 0, the
- issuer of the signers cert is always 1 etc… to the number of certificates-1.
- You can use this constant for readability in your code.
- }
-
- CONST
- kSIGSignerCertIndex = 0;
-
- {
- Call back procedure supplied by developer, return false to cancel the current
- process.
- }
- TYPE
- SIGStatusProcPtr = ProcPtr; { FUNCTION SIGStatus: BOOLEAN; }
- SIGStatusUPP = UniversalProcPtr;
-
- CONST
- uppSIGStatusProcInfo = $00000010; { FUNCTION : 1 byte result; }
-
- FUNCTION NewSIGStatusProc(userRoutine: SIGStatusProcPtr): SIGStatusUPP;
- {$IFC NOT GENERATINGCFM }
- INLINE $2E9F;
- {$ENDC}
-
- FUNCTION CallSIGStatusProc(userRoutine: SIGStatusUPP): BOOLEAN;
- {$IFC NOT GENERATINGCFM}
- INLINE $205F, $4E90;
- {$ENDC}
- {
- Resource id's of standard signature icon suite, all sizes and colors are available.
- }
-
- CONST
- kSIGSignatureIconResID = -16800;
- kSIGValidSignatureIconResID = -16799;
- kSIGInvalidSignatureIconResID = -16798;
-
- { ——————————————————————————————— CONTEXT CALLS ———————————————————————————————
- To use the Digital Signature toolbox you will need a SIGContextPtr. To create
- a SIGContextPtr you simply call SIGNewContext and it will create and initialize
- a context for you. To free the memory occupied by the context and invalidate
- its internal data, call SIGDisposeContext. An initialized context has no notion
- of the type of operation it will be performing however, once you call
- SIGSignPrepare SIGVerifyPrepare, or SIGDigestPrepare, the contexts operation
- type is set and to switch to another type of operation will require creating a
- new context. Be sure to pass the same context to corresponding toolbox calls
- (ie SIGSignPrepare, SIGProcessData, SIGSign) in other words mixing lets say
- signing and verify calls with the same context is not allowed.
- }
-
- FUNCTION SIGNewContext(VAR context: SIGContextPtr): OSErr;
- {$IFC NOT GENERATINGCFM}
- INLINE $203C, 2, 1900, $AA5D;
- {$ENDC}
- FUNCTION SIGDisposeContext(context: SIGContextPtr): OSErr;
- {$IFC NOT GENERATINGCFM}
- INLINE $203C, 2, 1901, $AA5D;
- {$ENDC}
- { ——————————————————————————————— SIGNING CALLS ———————————————————————————————
- Once you have created a SIGContextPtr, you create a signature by calling
- SIGSignPrepare once, followed by n calls to SIGProcessData, followed by one call
- toRcpt SIGSign. To create another signature on different data but for the same
- signer, don't dispose of the context and call SIGProcessData for the new data
- followed by a call SIGSign again. In this case the signer will not be prompted
- for their signer and password again as it was already provided. Once you call
- SIGDisposeContext, all signer information will be cleared out of the context and
- the signer will be re-prompted. The signer file FSSpecPtr should be set to nil
- if you want the toolbox to use the last signer by default or prompt for a signer
- if none exists. The prompt parameter can be used to pass a string to be displayed
- in the dialog that prompts the user for their password. If the substring "^1"
- (without the quotes) is in the prompt string, then the toolbox will replace it
- with the name of the signer from the signer selected by the user. If an empty
- string is passed, the following default string will be sent to the toolbox
- "\pSigning as ^1.". You can call any of the utility routines after SIGSignPrepare
- or SIGSign to get information about the signer or certs.
- }
- FUNCTION SIGSignPrepare(context: SIGContextPtr; {CONST}VAR signerFile: FSSpec; prompt: ConstStr255Param; VAR signatureSize: Size): OSErr;
- {$IFC NOT GENERATINGCFM}
- INLINE $203C, 8, 1902, $AA5D;
- {$ENDC}
- FUNCTION SIGSign(context: SIGContextPtr; signature: SIGSignaturePtr; statusProc: SIGStatusUPP): OSErr;
- {$IFC NOT GENERATINGCFM}
- INLINE $203C, 6, 1903, $AA5D;
- {$ENDC}
- { ——————————————————————————————— VERIFYING CALLS ———————————————————————————————
- Once you have created a SIGContextPtr, you verify a signature by calling
- SIGVerifyPrepare once, followed by n calls to SIGProcessData, followed by one
- call to SIGVerify. Check the return code from SIGVerify to see if the signature
- verified or not (noErr is returned on success otherwise the appropriate error
- code). Upon successfull verification, you can call any of the utility routines
- toRcpt find out who signed the data.
- }
- FUNCTION SIGVerifyPrepare(context: SIGContextPtr; signature: SIGSignaturePtr; signatureSize: Size; statusProc: SIGStatusUPP): OSErr;
- {$IFC NOT GENERATINGCFM}
- INLINE $203C, 8, 1904, $AA5D;
- {$ENDC}
- FUNCTION SIGVerify(context: SIGContextPtr): OSErr;
- {$IFC NOT GENERATINGCFM}
- INLINE $203C, 2, 1905, $AA5D;
- {$ENDC}
- { —————————————————————————————— DIGESTING CALLS ——————————————————————————————
- Once you have created a SIGContextPtr, you create a digest by calling
- SIGDigestPrepare once, followed by n calls to SIGProcessData, followed by one
- call to SIGDigest. You can dispose of the context after SIGDigest as the
- SIGDigestData does not reference back into it. SIGDigest returns the digest in
- digest.
- }
- FUNCTION SIGDigestPrepare(context: SIGContextPtr): OSErr;
- {$IFC NOT GENERATINGCFM}
- INLINE $203C, 2, 1906, $AA5D;
- {$ENDC}
- FUNCTION SIGDigest(context: SIGContextPtr; VAR digest: SIGDigestData): OSErr;
- {$IFC NOT GENERATINGCFM}
- INLINE $203C, 4, 1907, $AA5D;
- {$ENDC}
- { —————————————————————————————— PROCESSING DATA ——————————————————————————————
- To process data during a digest, sign, or verify operation call SIGProcessData
- as many times as necessary and with any sized blocks of data. The data needs to
- be processed in the same order during corresponding sign and verify operations
- but does not need to be processed in the same sized chunks (i.e., the toolbox
- just sees it as a continuous bit stream).
- }
- FUNCTION SIGProcessData(context: SIGContextPtr; data: UNIV Ptr; dataSize: Size): OSErr;
- {$IFC NOT GENERATINGCFM}
- INLINE $203C, 6, 1908, $AA5D;
- {$ENDC}
- { ——————————————————————————————— UTILITY CALLS ———————————————————————————————
- Given a context that has successfully performed a verification SIGShowSigner
- will display a modal dialog with the entire distinguished name of the person
- who signed the data. the prompt (if supplied) will appear at the top of the
- dialog. If no prompt is specified, the default prompt "\pVerification
- Successfull." will appear.
-
- Given a context that has been populated by calling SIGSignPrepare, SIGSign or a
- successful SIGVerify, you can make the remaining utility calls:
-
- SIGGetSignerInfo will return the SignerInfo record. The certCount can be used
- toRcpt index into the certificate set when calling SIGGetCertInfo,
- SIGGetCertNameAttributes or SIGGetCertIssuerNameAttributes. The signingTime is
- only defined if the call is made after SIGSign or SIGVerify. The certSetStatus
- will tell you the best status of the entire certificate set while
- certSetStatusTime will correspond to the time associated with that status (see
- definitions above).
-
- SIGGetCertInfo will return the SIGCertInfo record when given a valid index into
- the cert set in certIndex. Note: The cert at index kSIGSignerCertIndex is
- always the signers certificate. The serial number, start date and end date
- are there should you wish to display that info. The certAttributeCount and
- issuerAttributeCount provide the number of parts in the name of that certificate
- or that certificates issuer respectively. You use these numbers to index into
- either SIGGetCertNameAttributes or SIGGetCertIssuerNameAttributes to retrieve
- the name. The certStatus will tell you the status of the certificate while
- certStatusTime will correspond to the time associated with that status (see
- definitions above).
-
- SIGGetCertNameAttributes and SIGGetCertIssuerNameAttributes return name parts
- of the certificate at certIndex and attributeIndex. The newLevel return value
- tells you wether the name attribute returned is at the same level in the name
- hierarchy as the previous attribute. The type return value tells you the type
- of attribute returned. nameAttribute is the actual string containing the name
- attribute. So, if you wanted to display the entire distinguished name of the
- person who's signature was just validated you could do something like this;
-
- (…… variable declarations and verification code would preceed this sample ……)
-
- error = SIGGetCertInfo(verifyContext, kSIGSignerCertIndex, &certInfo);
- HandleErr(error);
-
- for (i = 0; i <= certInfo.certAttributeCount-1; i++)
- (
- error = SIGGetCertNameAttributes(
- verifyContext, kSIGSignerCertIndex, i, &newLevel, &type, theAttribute);
- HandleErr(error);
- DisplayNamePart(theAttribute, type, newLevel);
- )
- }
- FUNCTION SIGShowSigner(context: SIGContextPtr; prompt: ConstStr255Param): OSErr;
- {$IFC NOT GENERATINGCFM}
- INLINE $203C, 4, 1909, $AA5D;
- {$ENDC}
- FUNCTION SIGGetSignerInfo(context: SIGContextPtr; VAR signerInfo: SIGSignerInfo): OSErr;
- {$IFC NOT GENERATINGCFM}
- INLINE $203C, 4, 1910, $AA5D;
- {$ENDC}
- FUNCTION SIGGetCertInfo(context: SIGContextPtr; certIndex: LONGINT; VAR certInfo: SIGCertInfo): OSErr;
- {$IFC NOT GENERATINGCFM}
- INLINE $203C, 6, 1911, $AA5D;
- {$ENDC}
- FUNCTION SIGGetCertNameAttributes(context: SIGContextPtr; certIndex: LONGINT; attributeIndex: LONGINT; VAR attributeInfo: SIGNameAttributesInfo): OSErr;
- {$IFC NOT GENERATINGCFM}
- INLINE $203C, 8, 1912, $AA5D;
- {$ENDC}
- FUNCTION SIGGetCertIssuerNameAttributes(context: SIGContextPtr; certIndex: LONGINT; attributeIndex: LONGINT; VAR attributeInfo: SIGNameAttributesInfo): OSErr;
- {$IFC NOT GENERATINGCFM}
- INLINE $203C, 8, 1913, $AA5D;
- {$ENDC}
- { ——————————————————————————— FILE SIGN & VERIFY CALLS ——————————————————————————
- These calls allow you to detect the presence of a standard signtaure in a file as
- well as sign and verify files in a standard way. An example of this is the Finder,
- which uses these calls to allow the user to "drop sign" a file.
-
- To detect if a file is signed in the standard way, pass the FSSpec of the file to SIGFileIsSigned.
- A result of noErr means the file is in fact signed, otherwise, a kSIGNoSignature error will
- be returned.
-
- Once you have created a SIGContextPtr, you can make calls to either sign or verify a file in
- a standard way:
-
- To sign a file, call SIGSignPrepare followed by 'n' number of calls to SIGSignFile,
- passing it the file spec for each file you wish to sign in turn. You supply the context, the signature
- size that was returned from SIGSignPrepare and an optional call back proc. The call will take care of all
- the processing of data and affixing the signature to the file. If a signature already exists in the file,
- it is replaced with the newly created signature.
-
- To verify a file that was signed using SIGSignFile, call SIGVerifyFile passing it a new context and
- the file spec. Once this call has completed, if the verification is successfull, you can pass the context
- to SIGShowSigner to display the name of the person who signed the file.
- }
- FUNCTION SIGFileIsSigned({CONST}VAR fileSpec: FSSpec): OSErr;
- {$IFC NOT GENERATINGCFM}
- INLINE $203C, 2, 2500, $AA5D;
- {$ENDC}
- FUNCTION SIGSignFile(context: SIGContextPtr; signatureSize: Size; {CONST}VAR fileSpec: FSSpec; statusProc: SIGStatusUPP): OSErr;
- {$IFC NOT GENERATINGCFM}
- INLINE $203C, 8, 2501, $AA5D;
- {$ENDC}
- FUNCTION SIGVerifyFile(context: SIGContextPtr; {CONST}VAR fileSpec: FSSpec; statusProc: SIGStatusUPP): OSErr;
- {$IFC NOT GENERATINGCFM}
- INLINE $203C, 6, 2502, $AA5D;
- {$ENDC}
-
- {$ALIGN RESET}
- {$POP}
-
- {$SETC UsingIncludes := DigitalSignatureIncludes}
-
- {$ENDC} {__DIGITALSIGNATURE__}
-
- {$IFC NOT UsingIncludes}
- END.
- {$ENDC}
-